feat(harness): /orchestrator:setup — scaffold non-distributable residue (closes #37) - #45
Merged
Merged
Conversation
…residue (#37) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WNHtY86twXHEKsLEucSJyY
robercano
approved these changes
Jul 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an in-plugin
/orchestrator:setupskill that scaffolds into a consuming repo everything a Claude Code plugin cannot itself carry — the non-distributable residue — and absorbs the existing/setup-orchestratorinterview flow. Phase 2 of the packaging plan; builds on the #36 plugin skeleton.What it scaffolds (idempotently)
.claude/gates.json(project adapter) andCLAUDE.md..claude/workflows/feature-fanout.js, stamped with a version marker (below)..github/workflows/gates.yml+.github/actions/setup/action.yml, installed from templates stored under.claude/skills/setup/templates/(consumer-appropriate — the self-hostingself-gatesjob is stripped). Created if absent.module:*labels (viabot-gh.sh),.gitignoreentries (append-if-missing), and.claude/state/.MANAGED version marker (seam for #38)
templates/feature-fanout.jscarries// @orchestrator-managed feature-fanout v1.scaffold.shholds a singleMANAGED_VERSION=1source of truth and, on re-run: creates if absent, re-stamps when the destination marker is older/missing, reports "up to date" when equal, and never clobbers a newer marker. This is the seam phase 3 (#38) drives to push workflow fixes into already-onboarded repos.Idempotency
Re-running on an already-scaffolded repo changes nothing user-owned or CI, reports "up to date" for the managed workflow, and never duplicates
.gitignorelines.scaffold.shaccepts a target-dir arg (used for testing); reviewers verified fresh-run, no-op re-run, v0 re-stamp, v99 keep-newer, no-marker re-stamp, partial-gitignore append, and missing-template-surfaces-without-stub./setup-orchestratorreconciliationThe existing
.claude/commands/setup-orchestrator.mdis kept (frontmatter intact so it still resolves) but converted to a thin pointer that defers to the canonical flow now living in.claude/skills/setup/SKILL.md. The in-repo command surface the loop relies on is preserved.Boundary & non-breakage
All changes are under
.claude/**; no.github/**,docs/**, orexamples/**touched (CI ships as templates, not active workflows). Do-not-break scripts and the self-hosting flow are intact; self gates (build/lint/test) are green.Reviews
set -euo pipefail,bash -nclean, cwd-independent, deterministic across all exercised paths.Non-blocking follow-up noted by both:
.claude/skills/**sits outside the self-gate lint globs, so scaffold.sh/templates aren't auto-syntax-checked — consider wideningdo_lintlater.closes #37
🤖 Generated with Claude Code
https://claude.ai/code/session_01WNHtY86twXHEKsLEucSJyY